`svn st` for the root svn directory?

SVN doesn't have a notion of a project. It has directories and files, and you organize your project as you want in the repository. But SVN doesn't know that a particular directory is the root of a project You thus have to be in the right directory (or to pass it as an argument of svn st ) to have all the changes of the project.

SVN doesn't have a notion of a project. It has directories and files, and you organize your project as you want in the repository. But SVN doesn't know that a particular directory is the root of a project.

You thus have to be in the right directory (or to pass it as an argument of svn st) to have all the changes of the project.

– JB Nizet Mar 8 at 8:41 hg -C d args is equivalent to cd d && hg args && cd - – Elazar Leibovich Mar 8 at 9:06.

A simple workaround is defining $BASE to be the root checkout directory, and then using svn st $BASE. It wouldn't work when you're working on two subversion subdirectories. I came up with the following bash script to do more or less what I was looking for, note the backticks surrounding the pwd: $ cat svnb #!

/bin/sh PREVDIR=`pwd` while true; do if! -d . Svn ; then break; fi PREVDIR=`pwd` cd .. if "`pwd`" == "$PREVDIR" ; then break; fi done cd "$PREVDIR" if -d .

Svn ; then svn $@; else echo Not in an version controlled directory fi Usage example: $ cd example/s $ svnb st M base. C M s/inner. C $ cd / && svnb st Not in an version controlled directory.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.